Automatic hands free service requests

ABSTRACT

A service device processes a service request using account information of a user. The service device captures a first image of the user, generates a first user facial template based on the first image, and transmits the first user facial template with the account information to a service processing system. The user arrives at the service device to initiate a subsequent service request. The service device captures a second image of the user and generates a second user facial template based on the second image and searches for the first facial template matching the generated second facial template. The service device transmits a first stored matching facial template to the service processing system and a request for account information. The service device receives stored account information associated with the stored first facial template from the service processing system. The service device processes the subsequent service request using the account information.

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/369,161 filed Jul. 31, 2016, and entitled “Automatic Hands FreeService Requests,” the entire contents of which are hereby fullyincorporated herein by reference

TECHNICAL FIELD

The present disclosure relates to identify users making service requestsvia facial recognition.

BACKGROUND

When consumers make service requests at a service provider systemlocation, many methods of conducting a service request are available.Users may use many different cards or accounts for conducting servicerequests. The user account identifiers and other data represented by thecards may be communicated to a service provider computing device viamagnetic stripes of the cards, near field communication technologiesinvolving user computing devices, and other suitable mechanisms.

Current applications for processing service requests at a serviceprovider system location require a user to perform actions to identifyhimself by providing user account identifiers or other data to anoperator of a service provider system computing device.

SUMMARY

Techniques herein provide computer-implemented methods to identifyappropriate account information for use in service requests based onfacial recognition of users, the method comprising: receiving, by aservice provider computing device, account information associated with auser account and a request to process a first service request;processing, by the service provider computing device, the first servicerequest using the account information associated with the user account;capturing, by the service provider computing device and via a cameradevice communicatively coupled to the service provider computing device,a first image of the user associated with the user account; generating,by the service provider computing device, a first template comprising acomputer code representation of the first image of the user; deleting,by the service provider computing device, the first image of the userassociated with the user account; generating, by the service providercomputing device, a template identifier associated with the firsttemplate; transmitting, by the service provider computing device, thetemplate identifier and the account information associated with the useraccount to one or more computing devices; receiving, by the serviceprovider computing device, a request to process a second servicerequest; capturing, by the service provider computing device and via thecamera device, a second image of the user; generating, by the serviceprovider computing device, a second template based on the second imageof the user; identifying, by the service provider computing device, thefirst template from among a plurality of templates comprising the firsttemplate stored on the memory by comparing each template of theplurality of templates comprising the first template against the secondtemplate, wherein the similarity of the first template to the secondtemplate is greater than a threshold amount; determining, by the serviceprovider computing device, the template identifier associated with thefirst template; transmitting, to the one or more computing devices bythe service provider computing device, the template identifier and arequest for the account information associated with the user account;receiving, by the service provider computing device and from the one ormore computing devices, the requested account information associatedwith the user account, wherein the one or more computing devicestransmit the account information associated with the templateidentifier; and processing, by the service provider computing device,the requested second service request using the received accountinformation.

In some implementations the first image of the user comprises a firstfacial image of the user and the second image of the user comprises asecond facial image of the user.

In some implementations the account information comprises accountinformation, e.g., payment account information, wherein processing thefirst service request comprises processing a first transaction using theaccount information, and wherein processing the second service requestcomprises processing a second transaction using the account information.The first and second transactions can be payment transactions.

In some implementations comparing each template of the plurality oftemplates comprising the first template against the second templatecomprises comparing one or more particular regions of each templateagainst the one or more corresponding particular regions of the secondtemplate.

In some implementations the first template and the second templatecomprise computer code representations of the first user image and thesecond user image, respectfully.

In some implementations the method further comprises storing, by theservice provider computing device, the first template and the templateidentifier associated with the first template.

In some implementations capturing at least one of the first image of theuser and the second image of the user comprises capturing a video feedof a face of the user or surroundings of the camera device and a facialimage of the user is extracted from the captured video feed bydetermining a particular frame of the video feed and area of theinstance of the video feed corresponding to the face of the user andextracting the particular frame of the captured video.

In some implementations computer-implemented methods are provided toidentify users and associated information at a service provider locationbased on facial recognition. In an example embodiment, a user conducts aservice request at a service provider device at the service providersystem location. The user selects an account data type and providesaccount data. The service provider device processes a first servicerequest using the provided account data. The service provider devicedisplays a request to associate the account data with a user facialtemplate. If the user consents, the service provider device captures afirst image of the user's face using a camera device, generates a firstuser facial template based on the first user image, and stores the firstuser facial template. The service provider device transmits the firstuser facial template with the user payment account information to theservice provider system. The service provider system associates thefirst user facial template with the user account data. At a later time,the user arrives at the service provider device to conduct a subsequenttransaction. If the user consents to service request processing viafacial recognition, the service provider device operator selects anoption to determine the user account data based on facial recognition.The service provider device captures a second facial image of the userand generates a second user facial template based on the second facialimage of the user. The service provider device searches for the storedfirst facial template matching the generated second facial template. Ifthe service provider device finds a matching first stored facialtemplate, the service provider device transmits the first storedmatching facial template to the service provider system and a requestfor stored user account data. The service provider device receives thestored user account data associated with the stored first facialtemplate from the service provider system. The service provider deviceprocesses a subsequent transaction using the received user account dataassociated with the first user facial template.

In certain other example aspects described herein, systems and computerprogram products to identify appropriate account information for use inservice requests based on facial recognition of users are provided.

These and other aspects, objects, features, and advantages of theexample embodiments will become apparent to those having ordinary skillin the art upon consideration of the following detailed description ofillustrated example embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a system for identifying users andassociated payment account information at a merchant system locationbased on facial recognition, in accordance with certain exampleembodiments.

FIG. 2 is a block flow diagram depicting a method for identifying usersand associated payment account information at a merchant system locationbased on facial recognition, in accordance with certain exampleembodiments.

FIG. 3 is a block flow diagram depicting a method for conducting, by auser, a payment transaction at a merchant point of sale device, inaccordance with certain example embodiments.

FIG. 4 is a block flow diagram depicting a method for associatingpayment account information of a user with a user facial template, inaccordance with certain example embodiments.

FIG. 5 is a block flow diagram depicting a method for initiating, by auser, a subsequent payment transaction at a merchant location, inaccordance with certain example embodiments.

FIG. 6 is a block flow diagram depicting a method for processing asubsequent payment transaction with payment information determined basedon facial recognition of a user, in accordance with certain exampleembodiments.

FIG. 7 is a block diagram depicting a computing machine and module, inaccordance with certain example embodiments.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

The example embodiments described herein provide computer-implementedtechniques for identifying users and associated information at a serviceprovider location based on facial recognition.

In an example embodiment, a merchant system registers a merchant pointof sale device with a payment processing system. A user conducts apayment transaction at the merchant point of sale device at the merchantsystem location. For example, the user arrives at the merchant point ofsale device. The merchant point of sale device operator totals items ofthe user for purchase and asks the user to select a payment option. Theuser selects a payment option and provides payment account information.The merchant point of sale device transmits a payment authorizationrequest to an issuer system associated with the payment accountinformation. The issuer system receives the payment authorizationrequest and approves the payment authorization request. The merchantpoint of sale device receives a notice of approval of the paymentauthorization request from the issuer system and transmits a receipt tothe user. The merchant point of sale device displays a request toassociate the payment account information with a user facial template.If the user consents, the merchant point of sale device operator selectsan option to associate the user payment account information with a userfacial template. The merchant point of sale device captures a firstimage of the user's face using a camera device, generates a first userfacial template based on the first user image, and stores the first userfacial template. The merchant point of sale device deletes the firstuser image and transmits the first user facial template with the userpayment account information to the payment processing system. Thepayment processing system receives the first user facial template andthe user payment account information and associates the first userfacial template with the user payment account information. At a latertime, the user arrives at the merchant point of sale device to conduct asubsequent transaction. The merchant point of sale device operatortotals items of the user for purchase and displays a request for theuser to pay using facial recognition. If the user consents to paymentvia facial recognition, the merchant point of sale device operatorselects an option to determine the payment account information based onfacial recognition. The merchant point of sale device captures a secondfacial image of the user and generates a second user facial templatebased on the second facial image of the user. The merchant point of saledevice searches for the stored first facial template matching thegenerated second facial template. If the merchant point of sale devicefinds a matching first stored facial template, the merchant point ofsale device transmits the first stored matching facial template to thepayment processing system and a request for stored payment accountinformation. The merchant point of sale device receives the storedpayment account information associated with the stored first facialtemplate from the payment processing system. The merchant point of saledevice processes a subsequent transaction using the received paymentinformation associated with the first user facial template.

A merchant system registers with a payment processing system. In anexample, a merchant system operator installs a payment application on amerchant point of sale device. In another example, the merchant systemoperator installs the payment application on each of a plurality ofmerchant point of sale devices at a merchant system location. In yetanother example, the merchant system comprises a plurality of merchantsystem locations and one or more merchant system operators install thepayment application on each of one or more merchant point of saledevices at each of the plurality of merchant system locations. In anexample embodiment, the merchant system establishes a merchant systemaccount with the payment processing system. The merchant system mayprovide payment account information associated with one or more paymentaccounts associated with the merchant system to associate with themerchant system account.

A user conducts a payment transaction at a merchant point of sale deviceat a merchant system location. The user arrives at the merchant point ofsale device. For example, the user shops at the merchant system locationand identifies one or more products and/or services that the userdesires to purchase and approaches the merchant point of sale device topurchase the one or more items and/or services. The merchant point ofsale device operator totals the items of the user for purchase. Themerchant point of sale device operator asks the user to select a paymentoption. In an example, the merchant point of sale device operator scansor otherwise enters information associated with the one or more itemsthat the user desires to purchase and selects an interface object on theuser interface of the merchant point of sale device to cause themerchant point of sale device to total the items for purchase. In thisexample, the merchant point of sale device operator selects an object onthe user interface of the merchant point of sale device to initiate apayment transaction for the one or more items selected for purchase. Inthis example, the merchant point of sale device, in response to themerchant point of sale device operator selecting the option to initiatethe payment transaction, displays a request for a selection of a paymentoption.

The user selects a payment option and provides payment information. Inan example embodiment, the merchant point of sale device displays one ormore payment options for selection by the merchant point of sale deviceoperator or for selection by the user. Example payment options comprisepayment by credit card, payment by check, payment by debit card, paymentby gift card, payment by cash, and/or other applicable payment optionsaccepted at the merchant system location. In an example, the userdirects the merchant point of sale device operator to select a paymentoption desired by the user. For example, the user directs the merchantpoint of sale device operator to select an option to pay by credit card.In an example, the merchant point of sale device operator selects anobject on the user interface of the merchant point of sale device torequest payment via the payment option desired by the user. In anexample, in response to receiving an input of a selection of aparticular payment option, the merchant point of sale device displays arequest for payment information associated with the selected paymentoption. For example, the user directed the merchant point of sale deviceoperator to select a payment option to pay by credit card and themerchant point of sale device displays a request for payment cardinformation. The user may submit payment account information from apayment instrument such as a plastic card by swiping a magnetic stripeof a payment card at a reader of the merchant point of sale device orinserting a chip of a payment card at a chip reader of the merchantpoint of sale device. In another example, the user directs the merchantpoint of sale device operator to enter a payment account identifier asan input to the merchant point of sale device. In yet another example,the user may otherwise submit payment account information for theselected payment option. In an example, the merchant point of saledevice receives the payment account information input by the merchantpoint of sale device operator and/or input by the user. Payment accountinformation may comprise one or more of a payment account identifiercomprising alphanumeric and/or symbolic characters, an expiration date,a zip code associated with the payment account, a card verification codeor other security code, a personal identification number (“PIN”), anaddress associated with the payment account, a name associated with anaccount holder of the payment account, and/or biometric informationprovided by the user.

The merchant point of sale device transmits a payment authorizationrequest to an issuer system associated with the payment accountinformation. In another example, the merchant point of sale devicecommunicates information associated with the transaction to a paymentprocessing system and the payment processing system transmits thepayment authorization request to the issuer system via the network. Inan example, the issuer system is associated with the user paymentaccount selected for use in the transaction. For example, the issuersystem receives the payment authorization request from the merchantpoint of sale device or from the payment processing system over anetwork. The issuer system approves the payment authorization requestand transmits a payment authorization approval to merchant point of saledevice over the network. In another example, the issuer system transmitsthe payment authorization approval to the payment processing system overthe network and the payment processing system forwards the paymentauthorization approval to the merchant point of sale device over thenetwork. The merchant point of sale device transmits a receipt to theuser. In another example, the payment processing system receives thepayment authorization approval over the network and transmits atransaction receipt to the merchant point of sale device over thenetwork or transmits the transaction receipt directly to the user. Forexample, transmitting the receipt to the user comprises sending an emailto an email account of the user, printing a physical receipt via themerchant point of sale device for the merchant point of sale deviceoperator to hand to the user, or otherwise transmitting the receipt tothe user.

The merchant point of sale device displays a request to associate thepayment information from the completed transaction with a user facialtemplate. In an example, the merchant point of sale device displays therequest to associate the payment information with a user facial templateand provides, via a user interface, an option to consent to associatingthe payment information with a user facial template and an option todecline associating the payment information with a user facial template.If the user expresses a desire to decline associating the paymentinformation from the completed transaction with a user facial template,the merchant point of sale device operator selects the option not toassociate the payment information with a user facial template. In anexample, in response to receiving an input indicating that the user doesnot wish to associate the payment information with a user facialtemplate, the merchant point of sale device displays a messageindicating that the payment transaction is completed. For example, themerchant point of sale device displays a message reading “Thank you forshopping at Merchant A location!”

If the user expresses a desire to consent to associating the paymentinformation from the completed transaction with a user facial template,the merchant point of sale device operator selects the option toassociate the payment information with a user facial template. Themerchant point of sale device captures a facial image of the user usinga camera device. In an example, the merchant point of sale devicecaptures the facial image of the user in response to receiving the inputof the selection of the option to associate the payment information witha user facial template. In an example, the merchant point of sale devicecomprises the camera device. In another example, the camera device iscommunicatively coupled to the merchant point of sale device. Themerchant point of sale device generates a user facial template based onthe user facial image and stores the user facial template. In anexample, the user facial template comprises a computer coderepresentation of the user facial image. The merchant point of saledevice deletes the user facial image. The merchant point of sale devicetransmits the user facial template and the user payment accountinformation used in the completed transaction to the payment processingsystem. The payment processing system receives the user facial templateand the user payment account information and associates the user facialtemplate with the user payment account information. In an example, thepayment processing system stores the user facial template and userpayment account information in a memory of the payment processingsystem.

The user conducts a subsequent payment transaction at the merchantlocation with facial recognition. For example, the user arrives at themerchant point of sale device. In an example embodiment, the merchantpoint of sale device comprises the same merchant point of sale device atwhich the user conducted the completed transaction in which the userassociated payment account information with the facial template of theuser. In another example embodiment, the merchant point of sale devicecomprises a different merchant point of sale device at the same merchantsystem location at which the user conducted the completed transaction inwhich the user associated payment account information with the facialtemplate of the user. In yet another example embodiment, the merchantpoint of sale device comprises a different merchant point of sale devicethan the merchant point of sale device at which the user previouslyassociated the payment account information and the user facial templateand the different merchant point of sale device is located at adifferent merchant system location than the merchant system location atwhich the user associated the payment account information and the userfacial template.

The merchant point of sale device operator totals one or more items ofthe user for purchase and the merchant point of sale device displays arequest for the user to pay via facial recognition. In an example, themerchant point of sale device displays an option to pay via facialrecognition and an option to decline payment via facial recognition. Ifthe user indicates a desire to decline payment via facial recognition,the merchant point of sale device operator selects the option to declinepayment via facial recognition and the merchant point of sale devicedisplays a request for payment information. The user selects a paymentoption, for example, payment via credit account, bank account, or storeaccount, and provides payment information associated with the selectedpayment option. The merchant point of sale device processes atransaction.

If the user indicates a desire to consent to payment via facialrecognition, the merchant point of sale device determines paymentinformation based on facial recognition of the user. The merchant pointof sale device captures a facial image of the user. For example, themerchant point of sale device captures a facial image of the user usingthe camera device. In an example, the merchant point of sale devicecaptures the facial image of the user in response to receiving the inputof the selection of the option to consent to payment via facialrecognition. The merchant point of sale device generates a user facialtemplate based on the user facial image and stores the user facialtemplate. In an example, the user facial template comprises a computercode representation of the user facial image. In an example, themerchant point of sale device deletes the user facial image. Themerchant point of sale device searches for a stored user facial templatematching the generated user facial template. In an example embodiment,searching for a stored user facial template comprises searching on amemory of the merchant point of sale device, on a memory of one or moremerchant point of sale devices communicatively coupled to the merchantpoint of sale device, on a memory of the payment processing system, orsearching on any other appropriate memory of a computing devicecommunicatively coupled to or otherwise accessible to the merchant pointof sale device for storing user facial templates. In an exampleembodiment, searching for a matching stored user facial templatecomprises comparing one or more regions of the generated user facialtemplate to one or more corresponding regions of each of the stored userfacial templates.

If the merchant point of sale device is unable to find a stored userfacial template matching the generated user facial template, themerchant point of sale device operator asks the user to select a paymentoption and the user selects a payment option and provides paymentinformation. In this example, the merchant point of sale deviceprocesses a payment transaction using the payment information providedby the user. For example, the merchant point of sale device transmits apayment authorization request to an issuer system associated with thepayment information provided by the user. In this example, the issuersystem receives the payment authorization request and approves or deniesthe payment authorization request. The merchant point of sale devicereceives a notice of an approved or denied payment authorization requestand transmits a receipt to the user in accordance with the notice ofapproved or denied payment authorization request received from theissuer system.

If the merchant point of sale device finds a stored user facial templatematching the generated facial template, the merchant point of saledevice transmits a request for stored payment information associatedwith the generated user facial template to the payment processingsystem. In an example, the payment processing system receives thegenerated user facial template and finds a matching stored user facialtemplate that matches the received user facial template. For example,the payment processing system compares one or more regions of thereceived user facial template to one or more corresponding regions ofuser facial templates stored on a memory of the payment processingsystem. The payment processing system finds a matching stored userfacial template that matches the received user facial template andextracts stored payment information associated with the matching storeduser facial template. The payment processing system transmits theextracted payment information to the merchant point of sale device,which receives the payment information over the network. The merchantpoint of sale device transmits a payment authorization request to theissuer system associated with the received payment information. Inanother example, the payment processing system request transactiondetails from the merchant point of sale device, receives the transactiondetails from the merchant point of sale device, generates a paymentauthorization request based on the transaction details and the extractedpayment information, and transmits the payment authorization request tothe issuer system.

The issuer system receives the payment authorization request andapproves the payment authorization request. The issuer system transmitsa notice of approved payment authorization request to the merchant pointof sale device. In another example, the issuer system transmits a noticeof approved payment authorization request to the payment processingsystem and the payment processing system transmits the notice ofapproved payment authorization request to the merchant point of saledevice. The merchant point of sale device transmits a receipt to theuser. In another example, the payment processing system receives thepayment authorization approval over the network and transmits atransaction receipt to the merchant point of sale device over thenetwork or transmits the transaction receipt directly to the user. Forexample, transmitting the receipt to the user comprises sending an emailto an email account of the user, printing a physical receipt via themerchant point of sale device for the merchant point of sale deviceoperator to hand to the user, or otherwise transmitting the receipt tothe user.

By using and relying on the methods and systems described herein, theservice provider processing server, the service provider systemcomputing device, and the issuer system enable the user to conduct atransaction without the user having to interact with a mobile device ata service provider system location, as required in some currenttechnology. As such, the systems and methods described herein may reducethe inputs required by the user and the inputs required by the serviceprovider system computing device operator to identify the user.

Example System Architecture

Turning now to the drawings, in which like numerals indicate like (butnot necessarily identical) elements throughout the figures, exampleembodiments are described in detail.

FIG. 1 is a block diagram depicting a system 100 for identifying usersand associated payment account information at a merchant system locationbased on facial recognition, in accordance with certain exampleembodiments. As depicted in FIG. 1, the system 100 includes networkcomputing devices 110, 130, and 140 that are configured to communicatewith one another via one or more networks 120. In some embodiments, auser associated with a device must install an application and/or make afeature selection to obtain the benefits of the techniques describedherein.

In example embodiments, the network 120 can include a local area network(“LAN”), a wide area network (“WAN”), an intranet, an Internet, storagearea network (“SAN”), personal area network (“PAN”), a metropolitan areanetwork (“MAN”), a wireless local area network (“WLAN”), a virtualprivate network (“VPN”), a cellular or other mobile communicationnetwork, Bluetooth, Bluetooth low energy (“BLE”), near fieldcommunication (“NFC”), or any combination thereof or any otherappropriate architecture or system that facilitates the communication ofsignals, data, and/or messages. Throughout the discussion of exampleembodiments, it should be understood that the terms “data” and“information” are used interchangeably herein to refer to text, images,audio, video, or any other form of information that can exist in acomputer-based environment.

Each network computing device 110, 130, and 140 includes a device havinga communication module capable of transmitting and receiving data overthe network 120. For example, each network computing device 110, 130,and 140 can include a server, desktop computer, laptop computer, tabletcomputer, a television with one or more processors embedded thereinand/or coupled thereto, smart phone, handheld computer, personal digitalassistant (“PDA”), or any other wired or wireless, processor-drivendevice. In the example embodiment depicted in FIG. 1, the networkcomputing devices 110, 130, and 140 are operated by merchant point ofsale (“POS”) device 110 operators, issuer system 130 operators, andpayment processing system 140 operators, respectively.

An example merchant point of sale (“POS”) device 110, or serviceprovider device, comprises a camera device 111, payment application 113,a user interface 115, a data storage unit 116, and a communicationapplication 119.

In an example embodiment, the camera device 111 the camera device 111may be any component, application, or function of the merchant POSdevice 110 that captures a video input or captures a digital image of anexternal environment of the merchant camera device 111. In anotherexample embodiment, the camera device 111 is separate from the merchantPOS device 110 but communicatively coupled to the merchant POS device110. For example, the camera device 111 may be connected to the merchantPOS device 110 via the network 120. In an example, the camera device 111comprises a lens and an application that processes an input of anenvironment captured by the lens to produce an image. The camera device111 may be capable of obtaining individual images or a video scan. Anyother suitable image-capturing device may be represented by the cameradevice 111.

In an example embodiment, the payment application 113 is a program,function, routine, applet, or similar entity that exists on and performsits operations on the merchant point of sale device 110. In certainexample embodiments, the merchant POS device operator 102 or othermerchant system operator must install the payment application 113 and/ormake a feature selection on the merchant POS device 110 to obtain thebenefits of the techniques described herein. In an example embodiment,the merchant POS device operator 102 may access the payment application113 on the merchant POS device 110 via the user interface 115. In anexample embodiment, the payment application 113 may be associated withthe payment processing system 140.

In an example embodiment, the user interface 115 enables the merchantPOS device operator 102 to interact with the merchant POS device 110.For example, the user interface 115 may be a touch screen, a voice-basedinterface, or any other interface that allows the merchant POS deviceoperator 102 to provide input and receive output from an application onthe merchant POS device 110. In an example embodiment, the merchant POSdevice operator 102 interacts via the user interface 115 with thepayment application 113.

In an example embodiment, the data storage unit 116 comprises a local orremote data storage structure accessible to the merchant POS device 110suitable for storing information. In an example embodiment, the datastorage unit 116 stores encrypted information, such as HTML5 localstorage.

In an example embodiment, the communication application 119, such as aweb browser application or a stand-alone application, enables anoperator of the merchant POS device 110 to view, download, upload, orotherwise access documents or web pages via a distributed network 120.For example, the communication application 119 may enable communicationover the network 120 with the payment processing system 140.

An example issuer system 130 approves or denies a payment authorizationrequest received from the merchant POS device 110 or from the paymentprocessing system 140. In an example embodiment, the issuer system 130communicates with the merchant POS device 110 and/or payment processingsystem 140 over the network 120. In an example embodiment, the issuersystem 130 communicates with an acquirer system to approve a creditauthorization and to make payment to the payment processing system 140and/or merchant system. For example, the acquirer system is a thirdparty payment processing company.

An example payment processing system 140, or service provider system,comprises an account management component 141, a data storage unit 146,and a transaction processing component 147.

In an example embodiment, the account management component 141 receivesa user 101 facial template and payment account information used in aprevious transaction from the merchant POS device 120 and associates thereceived user 101 facial template with the received payment accountinformation. In an example, the account management component 141 storesthe user 101 facial template and associated payment account informationin a data storage unit 146 of the payment processing system 140. In anexample embodiment, the account management component 141 receives a user101 facial template from the merchant POS device 110 and finds amatching stored user 101 facial template that matches the received user101 facial template. In this example embodiment, the account managementcomponent 141 extracts stored payment information associated with thematching stored user 101 facial template. In an example, the accountmanagement component 141 transmits the extracted payment informationassociated with the matching user 101 facial template to the merchantPOS device 110. In another example, the account management component 141transmits the extracted payment information associated with the matchinguser 101 facial template to the transaction processing component 147.

In an example embodiment, the data storage unit 146 comprises a local orremote data storage structure accessible to the payment processingsystem 140 suitable for storing information. In an example embodiment,the data storage unit 166 stores encrypted information, such as HTML5local storage.

In an example embodiment, the transaction processing component 147receives transaction details from a merchant POS device 130 and paymentinformation associated with a user 101 facial template from the accountmanagement component 141. Example transaction details comprise merchantsystem account information and a total amount of the transaction. In anexample embodiment, the transaction processing component 147 transmits apayment authorization request to an issuer system 130 or otherappropriate financial institution associated with the payment accountinformation associated with the user 101 facial template. An examplepayment authorization request may comprise merchant system paymentaccount information, user 101 payment account information, and a totalamount of the transaction. In an example embodiment, after the issuersystem 130 processes the payment authorization request, the transactionprocessing component 147 receives an approval or denial of the paymentauthorization request from the issuer system 130 over the network 120.In an example embodiment, the transaction processing component 147transmits a receipt to the merchant POS device 110 comprising a summaryof the payment transaction.

In example embodiments, the network computing devices and any othercomputing machines associated with the technology presented herein maybe any type of computing machine such as, but not limited to, thosediscussed in more detail with respect to FIG. 7. Furthermore, anyfunctions, applications, or modules associated with any of thesecomputing machines, such as those described herein or any others (forexample, scripts, web content, software, firmware, or hardware)associated with the technology presented herein may by any of themodules discussed in more detail with respect to FIG. 7. The computingmachines discussed herein may communicate with one another, as well aswith other computing machines or communication systems over one or morenetworks, such as network 120. The network 120 may include any type ofdata or communications network, including any of the network technologydiscussed with respect to FIG. 7.

In example embodiments, the network computing devices and any othercomputing machines associated with the technology presented herein maybe any type of computing machine such as, but not limited to, thosediscussed in more detail with respect to FIG. 7. Furthermore, anyfunctions, applications, or components associated with any of thesecomputing machines, such as those described herein or any others (forexample, scripts, web content, software, firmware, hardware, or modules)associated with the technology presented herein may by any of thecomponents discussed in more detail with respect to FIG. 7. Thecomputing machines discussed herein may communicate with one another, aswell as with other computing machines or communication systems over oneor more networks, such as network 120. The network 120 may include anytype of data or communications network, including any of the networktechnology discussed with respect to FIG. 7.

Example Processes

The example methods illustrated in FIGS. 2-6 are described hereinafterwith respect to the components of the example operating environment 100.The example methods of FIGS. 2-6 may also be performed with othersystems and in other environments. The operations described with respectto any of the FIGS. 2-6 can be implemented as executable code stored ona computer or machine readable non-transitory tangible storage medium(e.g., floppy disk, hard disk, ROM, EEPROM, nonvolatile RAM, CD-ROM,etc.) that are completed based on execution of the code by a processorcircuit implemented using one or more integrated circuits; theoperations described herein also can be implemented as executable logicthat is encoded in one or more non-transitory tangible media forexecution (e.g., programmable logic arrays or devices, fieldprogrammable gate arrays, programmable array logic, application specificintegrated circuits, etc.).

FIG. 2 is a block diagram depicting a method 200 for identifying users101 and associated payment account information at a merchant systemlocation based on facial recognition, in accordance with certain exampleembodiments. The method 200 is described with reference to thecomponents illustrated in FIG. 1.

In block 210, the merchant system registers with the payment processingsystem 140. In an example embodiment, an agent of the merchant systemregisters for a merchant account with the payment processing system 140via a website of the payment processing system 140. In an exampleembodiment, the merchant system adds payment account information to themerchant account managed by the payment processing system 140. In anexample embodiment, the merchant system comprises one or more merchantsystem locations. For example, the merchant system may comprise one ormore physical store locations. An example merchant location comprisesone or more merchant point of sale (“POS”) devices 110. In an exampleembodiment, one or more merchant POS device operators 102 operate theone or more merchant POS devices 130 at each of the one or more merchantsystem locations.

In an example embodiment, a merchant system POS device operator 102installs the payment application 113 on the merchant POS device 110. Inanother example embodiment, the merchant system POS device operator 102purchases a merchant POS device 110 from the payment processing system140 or otherwise obtains the merchant POS device 110 with the paymentapplication 113 pre-installed on the merchant POS device 110. In anexample embodiment, the merchant POS device 110 is able to communicatewith the payment processing system 140, one or more issuer systems 130,and one or more acquirer systems over a network 120. In an exampleembodiment, the merchant POS device 110 communicates with the paymentprocessing system 140 via the payment application 113 over the network120. In certain example embodiments, the merchant POS device 110 may beable to transmit transaction details to the payment processing system140 via the payment application 113 over the network 120 to enable thepayment processing system 140 to process a transaction. In an exampleembodiment, the merchant POS device 110 receives a receipt from thepayment processing system 140 that notifies a merchant POS deviceoperator 102 as to whether a transaction was successful or not. In anexample embodiment, the merchant system installs the merchant POS device110 in an appropriate location at the merchant system location, forexample, in a checkout area of the merchant location.

In block 220, the user 101 conducts a payment transaction at a merchantPOS device 110 at a merchant system location. The method for conductinga payment transaction at a merchant point of sale device 110 at amerchant system location is described in more detail hereinafter withreference to the method described in FIG. 3.

FIG. 3 is a block diagram depicting a method 220 for conducting, by auser 101, a payment transaction at a merchant point of sale device 110,in accordance with certain example embodiments. The method 220 isdescribed with reference to the components illustrated in FIG. 1.

In block 310, the user 101 arrives at the merchant POS device 110. In anexample embodiment, the user 101 shops at the merchant location, selectsone or more items and/or services for purchase and presents the itemsand/or services to the merchant POS device operator 102 for purchase ata checkout area of the merchant location.

In bock 320, the merchant POS device operator 102 totals items of theuser 101 for purchase. For example, the merchant POS device operator 102scans barcodes or other machine-readable identifiers attached to theitems via the merchant POS device 110 or otherwise inputs informationassociated with the items into the merchant POS device 110. In anexample embodiment, the merchant POS device 110 displays a total amountfor the transaction. In this example embodiment, the merchant POS device110 may display information associated with each item such as a price,description of the item, and a quantity of the item.

In block 330, the merchant POS device operator 102 asks the user 101 toselect a payment option. In an example embodiment, the merchant POSdevice 110 displays, via a user interface 115 of the merchant POS device110, one or more objects on the user interface 115 corresponding to oneor more forms of payment accepted at the merchant location. A paymentoption may comprise payment by cash, payment by credit card, payment bybank account, payment by store account, payment by check, or any otherform of payment accepted by the merchant system for purchasetransactions at the merchant location.

In block 340, the user 101 selects a payment option and provides paymentaccount information. For example, the user 101 selects a payment optionto pay via credit card and provides the credit card or otherwiseprovides payment account information associated with the credit accountto the merchant POS device operator 102. In an example embodiment, themerchant POS device 110 operator may swipe a payment card, for example acredit card, debit card, gift card, store card, or other payment card,at a card reader of the merchant POS device 110 to transmit paymentaccount information from the payment card to the merchant POS device110. For example, the payment card may comprise a magnetic stripe orchip that is read by a card reader of the merchant POS device 110. Inanother example embodiment, the merchant POS device 110 operator mayscan a check provided by the user 101 or otherwise enter accountinformation associated with a bank account of the user into the merchantPOS device 110.

In block 350, the merchant POS device 110 transmits a paymentauthorization request to an issuer system 130 associated with thepayment account information. In an example embodiment, the merchant POSdevice 110 generates a payment authorization request comprising the user101 payment account information provided by the user, merchant systempayment account information, and a total amount of the transaction. Inan example embodiment, the issuer system 130 receives the paymentauthorization request from the merchant POS device 110 via the network120.

In another example embodiment, the merchant POS device 110 transmitstransaction details to the payment processing system 140 and the paymentprocessing system 140 generates the payment authorization request andtransmits the payment authorization request to the issuer system 130.For example, the merchant POS device 110 transmits transaction detailsto the payment processing system 140 comprising a transaction total, anaccount identifier of the merchant system, and the payment accountinformation provided by the user 101. In this example embodiment, thepayment processing system 140 receives the transaction details over thenetwork 120. In this example embodiment, the payment processing system140 transmits a payment authorization request to the issuer system 130.In this example embodiment, the payment processing system 140 generatesa payment authorization request comprising user 101 payment accountinformation, merchant system payment account information, and a totalamount of the transaction. In an example embodiment, the issuer system130 receives the payment authorization request from the paymentprocessing system 140 via the network 120.

In block 360, the issuer system 130 receives the payment authorizationrequest and approves the payment authorization request. In an exampleembodiment, the issuer system 130 receives the payment authorizationrequest from the payment processing system 140 or from the merchant POSdevice 110 via the network 120. In an example embodiment, the issuersystem 130 approves the payment authorization request and transmits apayment authorization approval notice to the payment processing system140 or to the merchant POS device 110. In an example embodiment, theissuer system 130 subtracts the user's 101 current account balance fromthe user's 101 credit limit associated with the user's 101 paymentaccount. In this example, if the different between the credit limit andthe credit balance is a positive number greater than the total amount ofthe transaction, the issuer system 130 approves the paymentauthorization. For example, the user 101 will not exceed his creditlimit if the transaction were to be approved, therefore the issuersystem 130 approves the payment authorization request. In an exampleembodiment, the payment processing system 140 or the merchant POS device110 receives the payment authorization approval from the issuer system130. In another example embodiment, the payment processing system 140 ormerchant POS device 110 receives a denial of the payment authorizationrequest in response to the issuer system 130 declining the paymentauthorization request. In an example embodiment, if the issuer system130 approves the payment authorization request, the issuer system 130credits the merchant system account and adds a charge to the user 101credit account, bank account or other payment account used by the user101 in the transaction.

In block 370, the merchant POS device 110 receives a notice of approvalof the payment authorization request from the issuer system 130. Forexample, the issuer system 130 generates the notice of approval of thepayment authorization request and transmits the notice of approval ofpayment authorization request to the merchant POS device 110 via thenetwork 120. In another example, the payment processing system 140transmits the notice of approval of payment authorization request to thepayment processing system 140 via the network 120 and the paymentprocessing system 140 transmits the notice to the merchant POS device110 via the network 120.

In block 380, the merchant POS device 110 transmits a receipt to theuser 101. For example, the merchant POS device 110 transmits the receiptto a user computing device associated with the user 101 for display onthe user computing device. In another example, the merchant POS device110 prints a receipt comprising a summary of the transaction via aprinter device that is a component of or otherwise communicativelycoupled to the merchant POS device 110.

From block 380, the method 220 proceeds to block 230 in FIG. 2.

Returning to FIG. 2, in block 230, the payment information of the user101 is associated with a user 101 facial template. The method forassociating payment account information of a user 101 with a user 101facial template is described in more detail hereinafter with referenceto the method described in FIG. 4.

FIG. 4 is a block diagram depicting a method 230 for associating paymentaccount information of a user 101 with a user 101 facial template, inaccordance with certain example embodiments. The method 230 is describedwith reference to the components illustrated in FIG. 1.

In block 410, the merchant POS device 110 displays a request toassociate user 101 payment information from the completed paymenttransaction with a user 101 facial template. For example, the merchantPOS device 110 displays a request, via the user interface 115, thatreads “would you like to sign up for payments with facial recognition?”In an example, the user 101 may ask the merchant POS device operator 102for information about the process for associating user 101 paymentinformation from the completed payment transaction with a user 101facial template.

In block 420, the user 101 decides whether to approve or decline therequest to associate the user 101 payment information from the completedtransaction with a user 101 facial template.

If the user declines the request to associate the user 101 paymentinformation from the completed transaction with a user 101 facialtemplate, the method 230 proceeds to block 430.

In block 430, the merchant POS device operator 102 selects an option notto associate the user 101 payment information from the completedtransaction with a user 101 facial template. For example, the user 101directs the merchant POS device operator 102 to select, via the userinterface 115 of the merchant POS device 110, an option to decline therequest to associate user 101 payment information from the completedpayment transaction with a user 101 facial template. In this example,the merchant POS device operator 102, selects the option to decline therequest in accordance with the decision of the user 101 by selecting anobject on the user interface 115 of the merchant POS Device 110. In anexample embodiment, if the merchant POS device operator 102 selects theoption not to associate the user 101 payment account information fromthe completed transaction with a user 101 facial template, the merchantPOS device 110 deletes the user 101 payment information. For example, inresponse to receiving an input of a selection of the option not toassociate the user 101 payment account information with a user 101facial template, the merchant POS device 110 deletes the payment accountinformation associated with the completed transaction or otherwise doesnot save the payment account information or transmit the payment accountinformation to the payment processing system 140 for association with auser 101 facial template.

Returning to block 420, if the user approves the request to associatethe user 101 payment information from the completed transaction with auser 101 facial template, the method 230 proceeds to block 440. In anexample embodiment, the merchant POS device operator 102 instructs theuser 101 position the user's 101 face such that a camera device 111 ofthe merchant POS device 110 or a camera device 111 otherwisecommunicatively coupled to the merchant POS device 110 may capture afacial image of the user 101. In this example embodiment, the user 101positions himself so that the camera device 111 may capture a facialimage of the user 101 in response to a selection by the merchant POSdevice operator 102 of a user interface 115 object.

In block 440, the merchant POS device operator 102 selects an option toassociate the user 101 payment information from the completedtransaction with a user 101 facial template. For example, the user 101directs the merchant POS device operator 102 to select, via the userinterface 115 of the merchant POS device 110, an option to accept therequest to associate user 101 payment information from the completedpayment transaction with a user 101 facial template. In this example,the merchant POS device operator 102 selects the option to accept therequest in accordance with the decision of the user 101 by selecting anobject on the user interface 115 of the merchant POS Device 110. In anexample embodiment, if the merchant POS device operator 102 selects theoption to associate the user 101 payment account information from thecompleted transaction with a user 101 facial template, the merchant POSdevice 110 deletes the user 101 payment information.

In block 450, the merchant POS device 110 captures a facial image of theuser 101. For example, in response to receiving an input of a selectionof the option to associate the user 101 payment account information witha user 101 facial template, the merchant POS device 110 activates acamera device 111 of the merchant POS device 110 or activates a cameradevice 111 communicatively coupled to the merchant POS device 110. In anexample embodiment, in response to receiving an input of a selection ofthe option to associate the user 101 payment account information with auser 101 facial template, the merchant POS device 110 instructs thecamera device 111 to capture an image of an environment of the cameradevice 110.

In an example embodiment, in response to receiving the input of theselection of the option to associate the user 101 payment accountinformation with a user 101 facial template, the merchant POS device 110begins to capture photo images and/or a video of the surroundings of thecamera device 111 via the camera device 111. In an example embodiment,the merchant POS device 110 captures a video feed of the user's 101 facevia the camera device 111. In another example embodiment, the merchantcamera device 1110 continuously captures, but does not record, a videofeed of its surroundings via the camera device 111. In this exampleembodiment, in response to receiving the input of the selection of theoption to associate the user 101 payment account information with a user101 facial template, the merchant POS device 110, via the camera device111, begins to record the video feed for a threshold amount of time. Inan example embodiment, the user 101 may be moving during the period inwhich the camera device 111 records the video feed. In an exampleembodiment, a processor of the camera device 111 extracts a facial imageby determining a particular frame of the video feed and area of theinstance of the video feed corresponding to the face of the user 101. Inan example embodiment, the camera device 111 extracts a facial image ofthe user 101 from the captured video. In an example embodiment, thecamera device 111 determines a frame of the captured video to provide animage of the user's 101 face and extracts the frame of the capturedvideo comprising the facial image of the user 101.

In block 460, the merchant POS device 110 generates a user 101 facialtemplate based on the user 101 facial image and stores the user 101facial template. In an example, the facial template is of apredetermined size, for example, a 128-byte facial template. In anexample, the merchant POS device 110 generates a facial templatecomprising a computer code representation of the digital facial image.For example, the facial template may describe key features of the facialimage of the user 101, such as shape, color, line, value, space, form,texture, or other useful or relevant feature of the image or ofparticular regions of the image. In another example, the facial templateis generated by processing the facial image through a convolutionalneural network. In an example, the facial template may describe keyfeatures of the facial image of the user 101, such as shape, color,line, value, space, form, texture, or other useful or relevant featureof the image or of particular regions of the image. In an exampleembodiment, the merchant POS device 110 stores the generated facialtemplate in a data storage unit 116 associated with the merchant POSdevice 110. For example, the merchant POS device 110 database maycomprise a log of facial templates. In an example embodiment, themerchant POS device 110 assigns a facial template identifier to the user101 facial template and associates the facial template identifier withthe stored user 101 facial template. In an example embodiment, themerchant POS device 110 stores the generated user 101 facial template ina memory or data storage unit accessible both by the merchant POS device110 and by one or more other merchant POS devices 110 at the merchantsystem location. In another example embodiment, the merchant POS device110 stores the generated user 101 facial template in a memory or datastorage unit accessible by the merchant POS device 110, by one or moreother merchant POS devices 110 at the merchant system location at whichthe completed transaction was conducted, and/or by one or more merchantPOS devices 110 at one or more other merchant system locations otherthan the merchant system location at which the completed transaction wasconducted. For example, the memory or data storage device may be a datastorage unit 116 on or communicatively coupled to the merchant POSdevice 110 or may be a memory or data storage accessible via the network120. In an example embodiment, the merchant POS device 110 stores thepayment account information from the completed transaction andassociates the stored payment account information with the stored facialtemplate. For example, the merchant POS device 110 stores the user 101facial template and the associated user 101 payment account informationfrom the completed transaction in a memory or data storage unitaccessible by the merchant POS device 110, by one or more other merchantPOS devices 110 at the merchant system location at which the completedtransaction was conducted, and/or by one or more merchant POS devices110 at one or more other merchant system locations other than themerchant system location at which the completed transaction wasconducted. In another example embodiment, the merchant POS device 110does not store the payment account information from the completedtransaction.

In block 470, the merchant POS device 110 deletes the user 101 facialimage. For example, the merchant POS device 110 and/or the camera device111 deletes the captured video and the extracted facial image. Forexample, the merchant POS device 110 and the camera device 111 do notstore captured images or video. In this example, facial templatesgenerated by the merchant POS device 110 comprise computer coderepresentations of facial images of users 101. In this example, aftergenerating a facial template or after a threshold time has passed aftercapturing video or images or extracting an image from a video, themerchant POS device 110 and/or the camera device 111 deletes anycaptured or extracted video or images.

In block 480, the merchant POS device 110 transmits the user 101 facialtemplate and the user 101 payment account information used in thecompleted transaction to the payment processing system 140. Aspreviously discussed, in some example embodiments, the merchant POSdevice 110 does not store the payment account information from thecompleted transaction. In an example embodiment, the merchant POS device110 transmits the user 101 facial template, a facial template identifierassociated with the user 101 facial template generated by the merchantPOS device 110, and the user 101 payment account information used in thecompleted transaction to the payment processing system via the network120.

In block 490, the payment processing system 140 receives the user 101facial template and the user 101 payment account information andassociates the user 101 facial template with the user 101 paymentaccount information. In an example embodiment, the payment processingsystem 140 receives the user 101 facial template, the facial templateidentifier associated with the user 101 facial template, and the user101 payment account information used in the completed transaction fromthe merchant POS device 110 over the network 120. In an exampleembodiment, the payment processing system 140 stores the received user101 facial template, the received facial template identifier associatedwith the received user 101 facial template, and the received user 101payment information used in the completed transaction in the datastorage unit 146 or other memory of the payment processing system 140.In an example embodiment, the payment processing system 140 associatesthe stored user 101 facial template and the stored user 101 paymentinformation with the stored facial template identifier.

From block 490, the method 230 proceeds to block 240 in FIG. 2.

Returning to FIG. 2, in block 240, the user 101 conducts a subsequenttransaction at the merchant location with facial recognition. The methodfor initiating a subsequent payment transaction at the merchant locationis described in more detail hereinafter with reference to the methoddescribed in FIG. 4.

FIG. 4 is a block diagram depicting a method 240 for initiating, by auser 101, a subsequent payment transaction at a merchant location, inaccordance with certain example embodiments. The method 240 is describedwith reference to the components illustrated in FIG. 1.

In block 510, the user 101 arrives at a merchant POS device 110. In anexample embodiment, the user 101 shops at the merchant location, selectsone or more items and/or services for purchase and presents the itemsand/or services to the merchant POS device operator 102 for purchase ata checkout area of the merchant location. In an example embodiment, theuser 101 in the subsequent payment transaction is the same user 101which conducted the completed transaction as described herein in blocks310-380. In an example embodiment, the merchant POS device 110 in thesubsequent payment transaction is the same merchant POS device 110involved in the completed transaction as described herein in blocks310-380. In another example embodiment, the merchant POS device 110 inthe subsequent payment transaction is a different merchant POS device110 from the merchant POS device 110 involved in the completedtransaction as described herein in blocks 310-380. For example, themerchant POS device 110 in the subsequent payment transaction is adifferent merchant POS device 110 at the same merchant location as themerchant POS device 110 involved in the completed transaction. Inanother example, the merchant POS device 110 in the subsequent paymenttransaction is a different merchant POS device 110 at a differentmerchant location than the merchant location where the merchant POSdevice 110 involved in the completed transaction is located.

In block 520, the merchant POS device operator 102 totals items of theuser 101 for purchase. For example, the merchant POS device operator 102scans barcodes or other machine-readable identifiers attached to theitems via the merchant POS device 110 or otherwise inputs informationassociated with the items into the merchant POS device 110. In anexample embodiment, the merchant POS device 110 displays a total amountfor the transaction. In this example embodiment, the merchant POS device110 may display information associated with each item such as a price,description of the item, and a quantity of the item.

In block 530, the merchant POS device 110 displays a request for theuser 101 to pay using facial recognition. For example, the merchant POSdevice 110 displays, via the user interface 115, a request that reads“would you like to pay using facial recognition?” or other appropriatelanguage that requests user 101 permission to capture a user 101 facialimage and identify stored payment account information based on a user101 facial template derived from the user 101 facial image. In anexample embodiment, the user 101 may ask the merchant POS deviceoperator 102 for information about making payments via facialrecognition to help in deciding whether or not to approve the request.In an example, the merchant POS device 110 displays a first object onthe user interface 115 that, when selected, indicates that the user 101allows payment via facial recognition and a second object on the userinterface 115 that, when selected, indicates that the user 101 does notconsent to payment via facial recognition.

In block 535, the user 101 decides whether to accept or decline therequest to pay using facial recognition.

If the user 101 declines to pay using facial recognition, the method 240proceeds to block 540. In an example embodiment, if the user 101declines to pay using facial recognition, the user 101 may select apayment option and provide payment account information via a paymentcard or otherwise provide payment account information to the merchantPOS device 110 to use in a transaction.

In block 540, the merchant POS device operator 102 selects an option onthe merchant POS device 110 not to determine payment account informationbased on facial recognition. In an example embodiment, the merchant POSdevice operator 102 selects an object displayed on the user interface115 that indicates that the user 101 does not want to pay via facialrecognition or otherwise does not want to determine payment accountinformation based on facial recognition.

In block 550, the merchant POS device 110 displays a request for paymentaccount information. In an example embodiment, the merchant POS device110 receives an input of the selection of the user interface 115 objectindicating the user's 101 denial of the request to determine paymentinformation based on facial recognition of the user 101. In this exampleembodiment, in response to receiving the input of the selection of theuser interface 115 object indicating the user's 101 denial of therequest to determine payment information based on facial recognition ofthe user 101, the merchant POS device 110 displays a request for paymentaccount information associated with a user 101 payment account.

In block 560, the user 101 selects a payment option and provides paymentinformation. For example, the merchant POS device operator 102 asks theuser 101 to select a payment option. In an example embodiment, themerchant POS device 110 displays, via a user interface 115 of themerchant POS device 110, one or more objects on the user interface 115corresponding to one or more forms of payment accepted at the merchantlocation. A payment option may comprise payment by cash, payment bycredit card, payment by bank account, payment by store account, paymentby check, or any other form of payment accepted by the merchant systemfor purchase transactions at the merchant location. In an exampleembodiment, the user 101 selects a payment option and provides paymentaccount information. For example, the user 101 selects a payment optionto pay via credit card and provides the credit card or otherwiseprovides payment account information associated with the credit accountto the merchant POS device operator 102. In an example embodiment, themerchant POS device 110 operator may swipe a payment card, for example acredit card, debit card, gift card, store card, or other payment card,at a card reader of the merchant POS device 110 to transmit paymentaccount information from the payment card to the merchant POS device110. For example, the payment card may comprise a magnetic stripe orchip that is read by a card reader of the merchant POS device 110. Inanother example embodiment, the merchant POS device 110 operator mayscan a check provided by the user 101 or otherwise enter accountinformation associated with a bank account of the user into the merchantPOS device 110

In block 570, the merchant POS device 110 processes a transaction. In anexample, the merchant POS device 110 transmits a payment authorizationrequest to an issuer system 130 associated with the payment accountinformation. In an example embodiment, the merchant POS device 110generates a payment authorization request comprising the user 101payment account information provided by the user, merchant systempayment account information, and a total amount of the transaction. Inan example embodiment, the issuer system 130 receives the paymentauthorization request from the merchant POS device 110 via the network120. In another example embodiment, the merchant POS device 110transmits transaction details to the payment processing system 140 andthe payment processing system 140 generates the payment authorizationrequest and transmits the payment authorization request to the issuersystem 130. For example, the merchant POS device 110 transmitstransaction details to the payment processing system 140 comprising atransaction total, an account identifier of the merchant system, and thepayment account information provided by the user 101. In this exampleembodiment, the payment processing system 140 receives the transactiondetails over the network 120. In this example embodiment, the paymentprocessing system 140 transmits a payment authorization request to theissuer system 130. In this example embodiment, the payment processingsystem 140 generates a payment authorization request comprising user 101payment account information, merchant system payment accountinformation, and a total amount of the transaction. In an exampleembodiment, the issuer system 130 receives the payment authorizationrequest from the payment processing system 140 via the network 120.

In an example embodiment, the issuer system 130 receives the paymentauthorization request and approves the payment authorization request. Inan example embodiment, the issuer system 130 receives the paymentauthorization request from the payment processing system 140 or from themerchant POS device 110 via the network 120. In an example embodiment,the issuer system 130 approves the payment authorization request andtransmits a payment authorization approval notice to the paymentprocessing system 140 or to the merchant POS device 110. In an exampleembodiment, the issuer system 130 subtracts the user's 101 currentaccount balance from the user's 101 credit limit associated with theuser's 101 payment account. In this example, if the different betweenthe credit limit and the credit balance is a positive number greaterthan the total amount of the transaction, the issuer system 130 approvesthe payment authorization. For example, the user 101 will not exceed hiscredit limit if the transaction were to be approved, therefore theissuer system 130 approves the payment authorization request. In anexample embodiment, the payment processing system 140 or the merchantPOS device 110 receives the payment authorization approval from theissuer system 130. In another example embodiment, the payment processingsystem 140 or merchant POS device 110 receives a denial of the paymentauthorization request in response to the issuer system 130 declining thepayment authorization request. In an example embodiment, if the issuersystem 130 approves the payment authorization request, the issuer system130 credits the merchant system account and adds a charge to the user101 credit account, bank account or other payment account used by theuser 101 in the transaction.

In an example, the merchant POS device 110 receives a notice of approvalof the payment authorization request from the issuer system 130. Forexample, the issuer system 130 generates the notice of approval of thepayment authorization request and transmits the notice of approval ofpayment authorization request to the merchant POS device 110 via thenetwork 120. In another example, the payment processing system 140transmits the notice of approval of payment authorization request to thepayment processing system 140 via the network 120 and the paymentprocessing system 140 transmits the notice to the merchant POS device110 via the network 120. The merchant POS device 110 may transmit areceipt to the user 101. For example, the merchant POS device 110transmits the receipt to a user computing device associated with theuser 101 for display on the user computing device. In another example,the merchant POS device 110 prints a receipt comprising a summary of thetransaction via a printer device that is a component of or otherwisecommunicatively coupled to the merchant POS device 110.

Returning to block 535, if the user 101 accepts the request to pay usingfacial recognition, the method 240 proceeds to block 580.

In block 580, the merchant POS device operator 102 selects an option onthe merchant POS device 110 to determine payment information based onfacial recognition. In an example embodiment, the merchant POS deviceoperator 102 selects an object displayed on the user interface 115 thatindicates that the user 101 approves the request to pay via facialrecognition or otherwise wants to determine payment account informationbased on facial recognition.

In block 590, the merchant POS device 110 processes a subsequenttransaction based on facial recognition of the user 101. The method forprocessing a subsequent payment transaction with payment informationdetermined based on facial recognition of a user 101 is described inmore detail hereinafter with reference to the method 590 described inFIG. 6.

FIG. 6 is a block diagram depicting a method 590 for processing asubsequent payment transaction with payment information determined basedon facial recognition of a user 101, in accordance with certain exampleembodiments. The method 590 is described with reference to thecomponents illustrated in FIG. 1.

In block 610, the merchant POS device 110 captures a facial image of theuser 101. In an example embodiment, the merchant POS device operator 102instructs the user 101 position the user's 101 face such that a cameradevice 111 of the merchant POS device 110 or a camera device 111otherwise communicatively coupled to the merchant POS device 110 maycapture a facial image of the user 101. In this example embodiment, theuser 101 positions himself so that the camera device 111 may capture afacial image of the user 101 in response to a selection by the merchantPOS device operator 102 of a user interface 115 object. In an example,the merchant POS device 110 captures a facial image of the user 101. Forexample, in response to receiving an input of a selection of the optionto associate the user 101 payment account information with a user 101facial template, the merchant POS device 110 activates a camera device111 of the merchant POS device 110 or activates a camera device 111communicatively coupled to the merchant POS device 110.

In an example embodiment, in response to receiving the input of theselection of the option to pay via facial recognition, the merchant POSdevice 110 begins to capture photo images and/or a video of thesurroundings of the camera device 111 via the camera device 111. In anexample embodiment, the merchant POS device 110 captures a video feed ofthe user's 101 face via the camera device 111. In another exampleembodiment, the merchant camera device 1110 continuously captures, butdoes not record, a video feed of its surroundings via the camera device111. In this example embodiment, in response to receiving the input ofthe selection of the option to associate the user 101 payment accountinformation with a user 101 facial template, the merchant POS device110, via the camera device 111, begins to record the video feed for athreshold amount of time. In an example embodiment, the user 101 may bemoving during the period in which the camera device 111 records thevideo feed. In an example embodiment, a processor of the camera device111 extracts a facial image by determining a particular frame of thevideo feed and area of the instance of the video feed corresponding tothe face of the user 101. In an example embodiment, the camera device111 extracts a facial image of the user 101 from the captured video. Inan example embodiment, the camera device 111 determines a frame of thecaptured video to provide an image of the user's 101 face and extractsthe frame of the captured video comprising the facial image of the user101.

In block 620, the merchant POS device 110 generates a user 101 facialtemplate based on the user 101 facial image. In an example, the facialtemplate is of a predetermined size, for example, a 128-byte facialtemplate. In an example, the merchant POS device 110 generates a facialtemplate comprising a computer code representation of the digital facialimage. For example, the facial template may describe key features of thefacial image of the user 101, such as shape, color, line, value, space,form, texture, or other useful or relevant feature of the image or ofparticular regions of the image. In another example, the facial templateis generated by processing the facial image through a convolutionalneural network. In an example, the facial template may describe keyfeatures of the facial image of the user 101, such as shape, color,line, value, space, form, texture, or other useful or relevant featureof the image or of particular regions of the image.

In block 630, the merchant POS device 110 searches for a stored user 101facial template matching the generated user 101 facial template. In anexample embodiment, the merchant POS device 110 searches for a storedfacial template matching the generated user 101 facial template in adata storage unit 116 associated with the merchant POS device 110. Forexample, the merchant POS device 110 database may comprise a log offacial templates. In an example embodiment, the merchant POS device 110searches for a stored user 101 facial template matching the generateduser 101 facial template in a memory or data storage unit accessibleboth by the merchant POS device 110 and by one or more other merchantPOS devices 110 at the merchant system location. In another exampleembodiment, the merchant POS device 110 searches for the stored user 101facial template matching the generated user 101 facial template in amemory or data storage unit accessible by the merchant POS device 110,by one or more other merchant POS devices 110 at the merchant systemlocation at which the completed transaction was conducted, and/or by oneor more merchant POS devices 110 at one or more other merchant systemlocations other than the merchant system location at which the completedtransaction was conducted. As previously discussed, the completedtransaction comprises the transaction wherein the user 101 facialtemplate was associated with user 101 payment account information usedin the completed transaction. For example, the memory or data storagedevice may be a data storage unit 116 on or communicatively coupled tothe merchant POS device 110 or may be a memory or data storage unitaccessible via the network 120.

In an example embodiment, to find a stored user 101 facial templatematching the generated user 101 facial template, the merchant POS device110 compares one or more regions of the generated user 101 facialtemplate against one or more corresponding regions of each of the storeduser 101 facial templates in one or more memories or data storage unitsaccessible by the merchant POS device 110 until the merchant POS device110 finds a stored user 101 facial template matching the generated user101 facial template. In an example, the generated user 101 facialtemplate and stored user 101 facial templates comprise computer coderepresentations of corresponding digital facial images upon which thegenerated user 101 facial template and the stored user 101 facialtemplates were based. For example, each user 101 facial template maydescribe key features of the facial image of the user 101, such asshape, color, line, value, space, form, texture, or other useful orrelevant feature of the image or of particular regions of the image. Forexample, each facial template was generated by processing the facialimage through a convolutional neural network. In an example, the facialtemplate may describe key features of the facial image of the user 101,such as shape, color, line, value, space, form, texture, or other usefulor relevant feature of the image or of particular regions of the image.

In block 635, the merchant POS device 110 determines whether themerchant POS device 110 found a stored user 101 facial template matchingthe generated user 101 facial template or did not find a stored user 101facial template matching the generated user 101 facial template. In anexample embodiment, the merchant POS device 110 searches for a storedfacial template matching the generated user 101 facial template in adata storage unit 116 associated with or otherwise accessible to themerchant POS device 110 by comparing the generated user 101 facialtemplate against each of the stored user 101 facial templates untilfinding a matching stored user 101 facial template that matches thegenerated user 101 facial template. In an example embodiment, thematching stored user 101 facial template is an exact match of thegenerated user 101 facial template. In another example embodiment, thematching stored user 101 facial template substantially matches thegenerated user 101 facial template. For example, to substantially match,the similarity between the generated user 101 facial template and thematching stored user 101 facial template must be greater than athreshold similarity. For example, the threshold similarity is 95percent or another appropriate threshold similarity determined by themerchant system. In an example embodiment, the merchant system mayconfigure the threshold similarity. For example, configuring a greaterthreshold similarity may increase the security of the transaction andthe certainty that the user 101 conducting the current transaction isthe same user 101 that conducted the previous, completed transaction.However, configuring a greater threshold similarity may result in asituation in which generated facial template of the user 101 does notmatch any stored user 101 facial templates even though the merchant POSdevice 110 previously stored a user 101 facial template for the user101. In another example, configuring a lesser threshold similarity mayresult in less occurrences of the situation in which the generatedfacial template of the user 101 does not match any stored user 101facial templates even though the merchant POS device 110 previouslystored a user 101 facial template for the user 101. However, configuringa lesser threshold similarity may also result in less security for thetransaction. In other example embodiments, to substantially match, thedifference between the generated user 101 facial template and thematching stored user 101 facial template must be less than a thresholddifference. For example, the threshold difference is five percent orother appropriate threshold difference determined by the merchantsystem.

If the merchant POS device 110 does not find a stored user 101 facialtemplate matching the generated user 101 facial template, the method 590returns to block 330 in FIG. 3. For example, the merchant POS device 110does not find a stored user 101 facial template that exactly orsubstantially matches the generated user 101 facial template. Forexample, none of the stored user 101 facial templates comprises asimilarity of greater than a 95 percent threshold similarity whencompared to the generated user 101 facial template, therefore themerchant POS device 110 determines that the merchant POS device 110cannot find a stored user 101 facial template matching the generateduser 101 facial template.

Returning to FIG. 6, in block 635, if the merchant POS device 110 findsa stored user 101 facial template matching the generated user 101 facialtemplate, the method 590 proceeds to block 640. For example, themerchant POS device 110 finds a stored user 101 facial template thatexactly or substantially matches the generated user 101 facial template.For example, the merchant POS device 110 finds a matching stored user101 facial template that comprises a similarity of greater than a 95percent threshold similarity when compared to the generated user 101facial template, therefore the merchant POS device 110 determines thatthe merchant POS device 110 found a stored user 101 facial templatematching the generated user 101 facial template.

In block 640, the merchant POS device 110 transmits a request for storedpayment account information associated with the matching stored user 101facial template to the payment processing system 140. In an exampleembodiment, the merchant POS device 110 extracts a stored user 101facial template identifier associated with the matching stored user 101facial template and transmits, to the payment processing system 140 viathe network 120, a request for stored payment account informationassociated with the stored user 101 facial template identifier. Inanother example embodiment, the merchant POS device 110 transmits thematching stored user 101 facial template to the payment processingsystem 140 via the network 120 along with a request for stored paymentaccount information associated with the matching stored user 101 facialtemplate. In yet another example embodiment, the merchant POS device 110transmits both the matching stored user 101 facial template and thestored user 101 facial template identifier associated with the matchingstored user 101 facial template to the payment processing system 140 viathe network 120 along with a request for stored payment accountinformation associated with the matching stored user 101 facialtemplate.

In an example embodiment, the payment processing system 140 receives therequest for stored payment account information and the received user 101facial template identifier and/or the received user 101 facial templatevia the network 120 from the merchant POS device 110. In an exampleembodiment, the payment processing system 140 identifies and extractspayment account information associated with the received user 101 facialtemplate or the received user 101 facial template identifier from a datastorage unit or memory accessible to the payment processing system 140.For example, the payment processing system 140 stores a list a user 101facial template identifiers and corresponding stored payment accountinformation associated with each respective user 101 facial templateidentifier. For example, the payment processing system 140 searches thelist to identify a user 101 facial template identifier matching thereceived user 101 facial template identifier. In this example, thepayment processing system 140 extracts the stored payment accountinformation associated with the matching user 101 facial templateidentifier.

In certain example embodiments, the payment processing system 140processes a transaction using the extracted payment account informationassociated with the user 101 facial template. In this exampleembodiment, the payment processing system 140 requests transactiondetails from the merchant POS device 110 via the network 120. In thisexample embodiment, the merchant POS device 110 receives the request fortransaction details from the payment processing system 140 via thenetwork 120 and transmits transaction details to the payment processingsystem 140 via the network 120. Example transaction details may comprisea total amount of transaction, a merchant system payment accountidentifier, and any other information necessary to process a transactioninvolving the extracted user 101 payment account information and themerchant system payment account information. In an example embodiment,the payment processing system transmits a payment authorization requestto the issuer system 130. In this example embodiment, the paymentprocessing system 140 generates a payment authorization requestcomprising the extracted user 101 payment account information, merchantsystem payment account information received in the transaction details,and a total amount of the transaction received in the transactiondetails. In an example embodiment, the issuer system 130 receives thepayment authorization request from the payment processing system 140 viathe network 120. In an example embodiment, the issuer system 130receives the payment authorization request from the payment processingsystem 140 or from the merchant POS device 110 via the network 120. Inan example embodiment, the issuer system 130 approves the paymentauthorization request and transmits a payment authorization approvalnotice to the payment processing system 140 or to the merchant POSdevice 110. In an example embodiment, the issuer system 130 subtractsthe user's 101 current account balance from the user's 101 credit limitassociated with the user's 101 payment account. In this example, if thedifferent between the credit limit and the credit balance is a positivenumber greater than the total amount of the transaction, the issuersystem 130 approves the payment authorization. For example, the user 101will not exceed his credit limit if the transaction were to be approved,therefore the issuer system 130 approves the payment authorizationrequest. In an example embodiment, the payment processing system 140 orthe merchant POS device 110 receives the payment authorization approvalfrom the issuer system 130. In another example embodiment, the paymentprocessing system 140 or merchant POS device 110 receives a denial ofthe payment authorization request in response to the issuer system 130declining the payment authorization request. In an example embodiment,if the issuer system 130 approves the payment authorization request, theissuer system 130 credits the merchant system account and adds a chargeto the user 101 credit account, bank account or other payment accountused by the user 101 in the transaction.

In an example, the merchant POS device 110 receives a notice of approvalof the payment authorization request from the issuer system 130. Forexample, the issuer system 130 generates the notice of approval of thepayment authorization request and transmits the notice of approval ofpayment authorization request to the merchant POS device 110 via thenetwork 120. In another example, the payment processing system 140transmits the notice of approval of payment authorization request to thepayment processing system 140 via the network 120 and the paymentprocessing system 140 transmits the notice to the merchant POS device110 via the network 120. The merchant POS device 110 may transmit areceipt to the user 101. For example, the merchant POS device 110transmits the receipt to a user computing device associated with theuser 101 for display on the user computing device. In another example,the merchant POS device 110 prints a receipt comprising a summary of thetransaction via a printer device that is a component of or otherwisecommunicatively coupled to the merchant POS device 110.

In certain other example embodiments, as described in blocks 650-690,however, the payment processing system 140 does not process thetransaction after extracting the user 101 payment account informationand instead transmits the extracted user 101 payment account informationto the merchant POS device 110 for the merchant POS device 110 toprocess the transaction.

In block 650, the merchant POS device 110 receives stored paymentaccount information associated with the matching stored user 101 facialtemplate from the payment processing system 140. In an exampleembodiment, the payment processing system 140 transmits, via the network120 and to the merchant POS device 110, the extracted payment accountinformation associated with the matching user 101 facial templateidentifier. For example, the payment processing system 140 received theuser 101 facial template and/or the user 101 facial template identifierfrom the merchant POS device 110 via the network 120 along with arequest for user 101 payment account information associated with thereceived user 101 facial template and the payment processing system 140extracts payment account information associated with the received user101 facial template or received user 101 facial template identifier andtransmits the extracted payment account information to the merchant POSdevice 110 via the network 120. In an example embodiment, the merchantPOS device 110 receives the payment account information associated withthe matching stored user 101 facial template and/or associated with thetransmitted user 101 facial template identifier from the paymentprocessing system 140 via the network 120.

In another example embodiment, in which the merchant POS device 110stores user 101 account information and associates the user 101 paymentaccount information from the completed transaction with the user 101facial template, the merchant POS device 110 does not transmits arequest for stored payment account information associated with thematching stored user 101 facial template to the payment processingsystem 140. Instead, in this example embodiment, the merchant POS device110 extracts the stored user 101 payment account information associatedwith the stored user 101 facial template that matches the generated user101 facial template. In this example embodiment, the merchant POS device110 does not communicate with the payment processing system 140 toretrieve the stored user 101 payment account information associated withthe stored user 101 facial template matching the generated user 101facial template. For example, the merchant POS device 110 extracts theuser 101 payment account information from the completed transactionassociated with the stored user 101 facial template matching thegenerated user 101 facial template from a memory or data storage unitaccessible by the merchant POS device 110.

In block 660, the merchant POS device 110 transmits a paymentauthorization request to the issuer system 130 associated with thereceived payment information. In an example embodiment, the merchant POSdevice 110 generates a payment authorization request comprising the user101 payment account information provided by the user, merchant systempayment account information, and a total amount of the transaction. Inan example embodiment, the issuer system 130 receives the paymentauthorization request from the merchant POS device 110 via the network120.

In block 670, the issuer system 130 receives the payment authorizationrequest and approves the payment authorization request. In an exampleembodiment, the issuer system 130 receives the payment authorizationrequest from the merchant POS device 110 via the network 120. In anexample embodiment, the issuer system 130 approves the paymentauthorization request and transmits a payment authorization approvalnotice to the payment processing system 140 or to the merchant POSdevice 110. In an example embodiment, the issuer system 130 subtractsthe user's 101 current account balance from the user's 101 credit limitassociated with the user's 101 payment account. In this example, if thedifferent between the credit limit and the credit balance is a positivenumber greater than the total amount of the transaction, the issuersystem 130 approves the payment authorization. For example, the user 101will not exceed his credit limit if the transaction were to be approved,therefore the issuer system 130 approves the payment authorizationrequest. In an example embodiment, the payment processing system 140 orthe merchant POS device 110 receives the payment authorization approvalfrom the issuer system 130. In another example embodiment, the paymentprocessing system 140 or merchant POS device 110 receives a denial ofthe payment authorization request in response to the issuer system 130declining the payment authorization request. In an example embodiment,if the issuer system 130 approves the payment authorization request, theissuer system 130 credits the merchant system account and adds a chargeto the user 101 credit account, bank account or other payment accountused by the user 101 in the transaction.

In block 680, the merchant POS device 110 receives notice of an approvedpayment authorization request from the issuer system 130. For example,the issuer system 130 generates the notice of approval of the paymentauthorization request and transmits the notice of approval of paymentauthorization request to the merchant POS device 110 via the network120. In another example, the payment processing system 140 transmits thenotice of approval of payment authorization request to the paymentprocessing system 140 via the network 120 and the payment processingsystem 140 transmits the notice to the merchant POS device 110 via thenetwork 120.

In block 690, the merchant POS device 110 transmits a receipt to theuser. For example, the merchant POS device 110 transmits the receipt toa user computing device associated with the user 101 for display on theuser computing device. In another example, the merchant POS device 110prints a receipt comprising a summary of the transaction via a printerdevice that is a component of or otherwise communicatively coupled tothe merchant POS device 110.

Other Example Embodiments

FIG. 7 depicts a computing machine 2000 and a module 2050 in accordancewith certain example embodiments. The computing machine 2000 maycorrespond to any of the various computers, servers, mobile devices,embedded systems, or computing systems presented herein. The module 2050may comprise one or more hardware or software elements configured tofacilitate the computing machine 2000 in performing the various methodsand processing functions presented herein. The computing machine 2000may include various internal or attached components such as a processor2010, system bus 2020, system memory 2030, storage media 2040,input/output interface 2060, and a network interface 2070 forcommunicating with a network 2080.

The computing machine 2000 may be implemented as a conventional computersystem, an embedded controller, a laptop, a server, a mobile device, asmartphone, a set-top box, a kiosk, a router or other network node, avehicular information system, one more processors associated with atelevision, a customized machine, any other hardware platform, or anycombination or multiplicity thereof. The computing machine 2000 may be adistributed system configured to function using multiple computingmachines interconnected via a data network or bus system.

The processor 2010 may be configured to execute code or instructions toperform the operations and functionality described herein, managerequest flow and address mappings, and to perform calculations andgenerate commands. The processor 2010 may be configured to monitor andcontrol the operation of the components in the computing machine 2000.The processor 2010 may be a general purpose processor, a processor core,a multiprocessor, a reconfigurable processor, a microcontroller, adigital signal processor (“DSP”), an application specific integratedcircuit (“ASIC”), a graphics processing unit (“GPU”), a fieldprogrammable gate array (“FPGA”), a programmable logic device (“PLD”), acontroller, a state machine, gated logic, discrete hardware components,any other processing unit, or any combination or multiplicity thereof.The processor 2010 may be a single processing unit, multiple processingunits, a single processing core, multiple processing cores, specialpurpose processing cores, co-processors, or any combination thereof.According to certain embodiments, the processor 2010 along with othercomponents of the computing machine 2000 may be a virtualized computingmachine executing within one or more other computing machines.

The system memory 2030 may include non-volatile memories such asread-only memory (“ROM”), programmable read-only memory (“PROM”),erasable programmable read-only memory (“EPROM”), flash memory, or anyother device capable of storing program instructions or data with orwithout applied power. The system memory 2030 may also include volatilememories such as random access memory (“RAM”), static random accessmemory (“SRAM”), dynamic random access memory (“DRAM”), and synchronousdynamic random access memory (“SDRAM”). Other types of RAM also may beused to implement the system memory 2030. The system memory 2030 may beimplemented using a single memory module or multiple memory modules.While the system memory 2030 is depicted as being part of the computingmachine 2000, one skilled in the art will recognize that the systemmemory 2030 may be separate from the computing machine 2000 withoutdeparting from the scope of the subject technology. It should also beappreciated that the system memory 2030 may include, or operate inconjunction with, a non-volatile storage device such as the storagemedia 2040.

The storage media 2040 may include a hard disk, a floppy disk, a compactdisc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), aBlu-ray disc, a magnetic tape, a flash memory, other non-volatile memorydevice, a solid state drive (“SSD”), any magnetic storage device, anyoptical storage device, any electrical storage device, any semiconductorstorage device, any physical-based storage device, any other datastorage device, or any combination or multiplicity thereof. The storagemedia 2040 may store one or more operating systems, application programsand program modules such as module 2050, data, or any other information.The storage media 2040 may be part of, or connected to, the computingmachine 2000. The storage media 2040 may also be part of one or moreother computing machines that are in communication with the computingmachine 2000 such as servers, database servers, cloud storage, networkattached storage, and so forth.

The module 2050 may comprise one or more hardware or software elementsconfigured to facilitate the computing machine 2000 with performing thevarious methods and processing functions presented herein. The module2050 may include one or more sequences of instructions stored assoftware or firmware in association with the system memory 2030, thestorage media 2040, or both. The storage media 2040 may thereforerepresent examples of machine or computer readable media on whichinstructions or code may be stored for execution by the processor 2010.Machine or computer readable media may generally refer to any medium ormedia used to provide instructions to the processor 2010. Such machineor computer readable media associated with the module 2050 may comprisea computer software product. It should be appreciated that a computersoftware product comprising the module 2050 may also be associated withone or more processes or methods for delivering the module 2050 to thecomputing machine 2000 via the network 2080, any signal-bearing medium,or any other communication or delivery technology. The module 2050 mayalso comprise hardware circuits or information for configuring hardwarecircuits such as microcode or configuration information for an FPGA orother PLD.

The input/output (“I/O”) interface 2060 may be configured to couple toone or more external devices, to receive data from the one or moreexternal devices, and to send data to the one or more external devices.Such external devices along with the various internal devices may alsobe known as peripheral devices. The I/O interface 2060 may include bothelectrical and physical connections for operably coupling the variousperipheral devices to the computing machine 2000 or the processor 2010.The I/O interface 2060 may be configured to communicate data, addresses,and control signals between the peripheral devices, the computingmachine 2000, or the processor 2010. The I/O interface 2060 may beconfigured to implement any standard interface, such as small computersystem interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel,peripheral component interconnect (“PCP”), PCI express (PCIe), serialbus, parallel bus, advanced technology attached (“ATA”), serial ATA(“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, variousvideo buses, and the like. The I/O interface 2060 may be configured toimplement only one interface or bus technology. Alternatively, the I/Ointerface 2060 may be configured to implement multiple interfaces or bustechnologies. The I/O interface 2060 may be configured as part of, allof, or to operate in conjunction with, the system bus 2020. The I/Ointerface 2060 may include one or more buffers for bufferingtransmissions between one or more external devices, internal devices,the computing machine 2000, or the processor 2010.

The I/O interface 2060 may couple the computing machine 2000 to variousinput devices including mice, touch-screens, scanners, electronicdigitizers, sensors, receivers, touchpads, trackballs, cameras,microphones, keyboards, any other pointing devices, or any combinationsthereof. The I/O interface 2060 may couple the computing machine 2000 tovarious output devices including video displays, speakers, printers,projectors, tactile feedback devices, automation control, roboticcomponents, actuators, motors, fans, solenoids, valves, pumps,transmitters, signal emitters, lights, and so forth.

The computing machine 2000 may operate in a networked environment usinglogical connections through the network interface 2070 to one or moreother systems or computing machines across the network 2080. The network2080 may include wide area networks (WAN), local area networks (LAN),intranets, the Internet, wireless access networks, wired networks,mobile networks, telephone networks, optical networks, or combinationsthereof. The network 2080 may be packet switched, circuit switched, ofany topology, and may use any communication protocol. Communicationlinks within the network 2080 may involve various digital or an analogcommunication media such as fiber optic cables, free-space optics,waveguides, electrical conductors, wireless links, antennas,radio-frequency communications, and so forth.

The processor 2010 may be connected to the other elements of thecomputing machine 2000 or the various peripherals discussed hereinthrough the system bus 2020. It should be appreciated that the systembus 2020 may be within the processor 2010, outside the processor 2010,or both. According to certain example embodiments, any of the processor2010, the other elements of the computing machine 2000, or the variousperipherals discussed herein may be integrated into a single device suchas a system on chip (“SOC”), system on package (“SOP”), or ASIC device.

In situations in which the systems discussed here collect personalinformation about users, or may make use of personal information, theusers may be provided with an opportunity or option to control whetherprograms or features collect user information (e.g., information about auser's social network, social actions or activities, profession, auser's preferences, or a user's current location), or to control whetherand/or how to receive content from the content server that may be morerelevant to the user. In addition, certain data may be treated in one ormore ways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over how information is collected about the userand used by a content server.

Embodiments may comprise a computer program that embodies the functionsdescribed and illustrated herein, wherein the computer program isimplemented in a computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.However, it should be apparent that there could be many different waysof implementing embodiments in computer programming, and the embodimentsshould not be construed as limited to any one set of computer programinstructions. Further, a skilled programmer would be able to write sucha computer program to implement an embodiment of the disclosedembodiments based on the appended flow charts and associated descriptionin the application text. Therefore, disclosure of a particular set ofprogram code instructions is not considered necessary for an adequateunderstanding of how to make and use embodiments. Further, those skilledin the art will appreciate that one or more aspects of embodimentsdescribed herein may be performed by hardware, software, or acombination thereof, as may be embodied in one or more computingsystems. Moreover, any reference to an act being performed by a computershould not be construed as being performed by a single computer as morethan one computer may perform the act.

The example embodiments described herein can be used with computerhardware and software that perform the methods and processing functionsdescribed herein. The systems, methods, and procedures described hereincan be embodied in a programmable computer, computer-executablesoftware, or digital circuitry. The software can be stored oncomputer-readable media. For example, computer-readable media caninclude a floppy disk, RAM, ROM, hard disk, removable media, flashmemory, memory stick, optical media, magneto-optical media, CD-ROM, etc.Digital circuitry can include integrated circuits, gate arrays, buildingblock logic, field programmable gate arrays (FPGA), etc.

The example systems, methods, and acts described in the embodimentspresented previously are illustrative, and, in alternative embodiments,certain acts can be performed in a different order, in parallel with oneanother, omitted entirely, and/or combined between different exampleembodiments, and/or certain additional acts can be performed, withoutdeparting from the scope and spirit of various embodiments. Accordingly,such alternative embodiments are included in the scope of the followingclaims, which are to be accorded the broadest interpretation so as toencompass such alternate embodiments.

Although specific embodiments have been described above in detail, thedescription is merely for purposes of illustration. It should beappreciated, therefore, that many aspects described above are notintended as required or essential elements unless explicitly statedotherwise. Modifications of, and equivalent components or actscorresponding to, the disclosed aspects of the example embodiments, inaddition to those described above, can be made by a person of ordinaryskill in the art, having the benefit of the present disclosure, withoutdeparting from the spirit and scope of embodiments defined in thefollowing claims, the scope of which is to be accorded the broadestinterpretation so as to encompass such modifications and equivalentstructures.

What is claimed is:
 1. A computer-implemented method to identifyappropriate account information for use in service requests based onfacial recognition of users, comprising: receiving, by a serviceprovider computing device, account information associated with a useraccount and a request to process a first service request; processing, bythe service provider computing device, the first service request usingthe account information associated with the user account; capturing, bythe service provider computing device and via a camera devicecommunicatively coupled to the service provider computing device, afirst image of the user associated with the user account; generating, bythe service provider computing device, a first template comprising acomputer code representation of the first image of the user; deleting,by the service provider computing device, the first image of the userassociated with the user account; generating, by the service providercomputing device, a template identifier associated with the firsttemplate; transmitting, by the service provider computing device, thetemplate identifier and the account information associated with the useraccount to one or more computing devices; receiving, by the serviceprovider computing device, a request to process a second servicerequest; capturing, by the service provider computing device and via thecamera device, a second image of the user; generating, by the serviceprovider computing device, a second template based on the second imageof the user; identifying, by the service provider computing device, thefirst template from among a plurality of templates comprising the firsttemplate stored on the memory by comparing each template of theplurality of templates comprising the first template against the secondtemplate, wherein the similarity of the first template to the secondtemplate is greater than a threshold amount; determining, by the serviceprovider computing device, the template identifier associated with thefirst template; transmitting, to the one or more computing devices bythe service provider computing device, the template identifier and arequest for the account information associated with the user account;receiving, by the service provider computing device and from the one ormore computing devices, the requested account information associatedwith the user account, wherein the one or more computing devicestransmit the account information associated with the templateidentifier; and processing, by the service provider computing device,the requested second service request using the received accountinformation.
 2. The method of claim 1, wherein the first image of theuser comprises a first facial image of the user and wherein the secondimage of the user comprises a second facial image of the user.
 3. Themethod of claim 1, wherein processing the first service requestcomprises processing a first transaction using the account information,and wherein processing the second service request comprises processing asecond transaction using the account information.
 4. The method of claim1, wherein comparing each template of the plurality of templatescomprising the first template against the second template comprisescomparing one or more particular regions of each template against theone or more corresponding particular regions of the second template. 5.The method of claim 1, wherein the first template and the secondtemplate comprise computer code representations of the first user imageand the second user image, respectfully.
 6. The method of claim 1,further comprising storing, by the service provider computing device,the first template and the template identifier associated with the firsttemplate.
 7. The method of claim 1, wherein capturing at least one ofthe first image of the user and the second image of the user comprisescapturing a video feed of a face of the user or surroundings of thecamera device and a facial image of the user is extracted from thecaptured video feed by determining a particular frame of the video feedand area of the instance of the video feed corresponding to the face ofthe user and extracting the particular frame of the captured video.
 8. Acomputer program product to identify appropriate account information foruse in service requests based on facial recognition of users,comprising: a non-transitory computer-readable medium havingcomputer-executable program instructions embodied thereon that whenexecuted by a computer cause the computer to: generate a first templatecomprising a computer code representation of a first image of a user;generate a template identifier associated with the first template;transmit the template identifier and account information associated withan account of the user to one or more computing devices; receive arequest to process a service request; capture, via a camera device, asecond image of the user; generate a second template based on the secondimage of the user; identify the first template from among a plurality oftemplates comprising the first template stored on a memory by comparingeach template of the plurality of templates comprising the firsttemplate against the second template, wherein a similarity of the firsttemplate to the second template is greater than a threshold amount;determine the template identifier associated with the first template;transmit, to the one or more computing devices, the template identifierand a request for the account information associated with the account;receive, from the one or more computing devices, the account informationassociated with the user account, wherein the one or more computingdevices transmit the account information associated with the templateidentifier; and process the requested service request using the receivedaccount information.
 9. The computer program product of claim 8, whereinthe non-transitory computer-readable medium further comprisescomputer-executable program instructions embodied thereon that whenexecuted by the computer cause the computer to: receive, at a timebefore generating the first template, the account information associatedwith the user account and a request to process a prior service request;process the prior service request using the account informationassociated with the account; capture, via the camera device the firstimage of the user associated with the user account, the camera devicecommunicatively coupled to the service provider computing device; and ata time after generating the first template, delete the first image ofthe user associated with the account.
 10. The computer program productof claim 9, wherein processing the prior service request comprisesprocessing a first transaction using the account information, andwherein processing the service request comprises processing a secondtransaction using the account information.
 11. The computer programproduct of claim 8, wherein the non-transitory computer-readable mediumfurther comprises computer-executable program instructions embodiedthereon that when executed by the computer cause the computer to storethe first template and the template identifier associated with the firsttemplate.
 12. The computer program product of claim 8, wherein the firstimage of the user comprises a first facial image of the user and whereinthe second image of the user comprises a second facial image of theuser.
 13. The computer program product of claim 8, wherein comparingeach template of the plurality of templates comprising the firsttemplate against the second template comprises comparing one or moreparticular regions of each template against the one or morecorresponding particular regions of the second template.
 14. Thecomputer program product of claim 8, wherein the first template and thesecond template comprise computer code representations of the first userimage and the second user image, respectfully.
 15. The computer programproduct of claim 8, wherein capturing at least one of the first image ofthe user and the second image of the user comprises capturing a videofeed of the face of the user or surroundings of the camera device andthe computer-executable program instructions comprisescomputer-executable program instructions to extract a facial image ofthe user from the captured video feed by determining a particular frameof the video feed and area of the instance of the video feedcorresponding to the face of the user and extracting the particularframe of the captured video.
 16. A system to identify appropriateaccount information for use in service requests based on facialrecognition of users, comprising: a storage device; and a processorcommunicatively coupled to the storage device, wherein the processorexecutes application code instructions that are stored in the storagedevice to cause the system to: generate a first template comprising acomputer code representation of a first image of a user; generate atemplate identifier associated with the first template; transmit thetemplate identifier and account information associated with an accountassociated with the user to one or more computing devices; receive arequest to process a service request; capture, via a camera device, asecond image of the user; generate a second template based on the secondimage of the user; identify the first template from among a plurality oftemplates comprising the first template stored on a memory by comparingeach template of the plurality of templates comprising the firsttemplate against the second template, wherein a similarity of the firsttemplate to the second template is greater than a threshold amount;determine the template identifier associated with the first template;transmit, to the one or more computing devices, the template identifierand a request for the account information associated with the useraccount; receive, from the one or more computing devices, the requestedaccount information associated with the account, wherein the one or morecomputing devices transmit the account information associated with thetemplate identifier; and process the requested service request using thereceived account information.
 17. The system of claim 16, wherein theprocessor is further configured to execute computer-readable programinstructions stored in the storage device to cause the system to storethe first template and the template identifier associated with the firsttemplate.
 18. The system of claim 16, wherein the first image of theuser comprises a first facial image of the user and wherein the secondimage of the user comprises a second facial image of the user.
 19. Thesystem of claim 16, wherein processing the service request comprisesprocessing a transaction using the received account information.
 20. Thesystem of claim 16, wherein comparing each template of the plurality oftemplates comprising the first template against the second templatecomprises comparing one or more particular regions of each templateagainst the one or more corresponding particular regions of the secondtemplate.
 21. The system of claim 16, wherein the first template and thesecond template comprise computer code representations of the first userimage and the second user image, respectfully.
 22. The system of claim16, wherein capturing at least one of the first image of the user andthe second image of the user comprises capturing a video feed of a faceof the user or surroundings of the camera device and the applicationcode instructions that are stored in the storage device further causethe system to extract a facial image of the user from the captured videofeed by determining a particular frame of the video feed and area of theinstance of the video feed corresponding to the face of the user andextracting the particular frame of the captured video.